An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hi all. I'm a solo developer of an iOS fitness app and I just got rejected under Guideline 5.1.2(i). I'd really appreciate some guidance, because I think I understand the rejection but I'm not sure of the right way to handle it. Here's what App Review said: "The app does not use App Tracking Transparency to request the user's permission before collecting data used to track them. Instead, the app displays a custom prompt that requests the user to allow tracking." The prompt they're talking about is a sheet I show that asks "Share usage data?" and lets the person say yes or no. Nothing is sent to our analytics provider unless they say yes. The reason I'm confused is that I don't think my app tracks anyone by Apple's definition (and a few other posts I saw online say that PostHog doesn't fall under this category). The way I read it, tracking means linking data from my app with other companies' data for targeted advertising or ad measurement, or sharing it with data brokers. My app: - Has no ads and no ad SDKs - Doesn't use the advertising identifier (IDFA) - Doesn't combine user data with other companies' data - Doesn't share data with data brokers - Declares no tracking in its privacy manifest and App Privacy label The prompt is only for product analytics through PostHog, so I can see things like which screens and features get used. Those events are tied to a random account ID. They don't include workout totals, health readings or cycle data. I asked for permission because I thought it was the right thing to do for a health and fitness app, and because Guideline 5.1.2(i) says to get permission before sharing data with third parties. It seems like the prompt may have been read as asking to track, when it's really asking for permission for analytics that aren't tracking. My plan for the resubmission is to remove the prompt, explain that in my notes, and leave a switch in Settings that's off by default. The downside is that almost nobody will ever turn it on, so I'd have very little data on how people use the app. My questions: 1. Is a custom prompt allowed when it asks permission for first-party product analytics and not tracking? Has anyone gotten one approved, and did specific wording or a note to App Review help? 2. If the app really doesn't track, is removing the prompt and explaining that in the review notes the right way to resolve this? 3. Would it be wrong to use the App Tracking Transparency prompt here? My understanding is that it's only for apps that actually track, and using it would wrongly suggest that mine does. 4. Is an off-by-default switch in Settings enough permission for analytics like this? Or is there a better way to ask that App Review is comfortable with? If anyone has been through this, or anyone from Apple can point me in the right direction, I'd really appreciate it. I want to do this the right way. Thanks!

Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.

I hope this informafion helps! Timeframe for existing apps are said to be around 24-72 hours for review. HOWEVER, for new apps, there possibly may be a wait time of around 13-22 days🙂 see attached images?

Our app, Unscroll, has an auto-renewable monthly subscription. Users set a daily time limit inside the app. We plan to give a monthly subscriber a free next month through a promotional offer (type: Free, duration: 1 month) when they stayed within their limit on at least 20 days of the current subscription period. Eligibility is computed on the device from the app's own measurement of time spent inside Unscroll. We do not use Screen Time, Family Controls or DeviceActivity data for it. Every paid feature stays available to every subscriber. The free month is an extra, and nothing depends on it. The offer is shown inside the app; notifications are not required. The full monthly price is shown first on the subscription screen, with the condition written next to it. Questions: Is this use of promotional offers acceptable under App Review Guidelines 3.1.1, 3.1.2 and 3.2.2(x)? Can the same customer redeem the same free promotional offer again in later periods (once per qualifying period)? For an active monthly subscriber, does a free promotional offer for the same product take effect at the next renewal date? Thank you.

CapDrive 1.2.1 (Build 27) has been repeatedly rejected under Guideline 2.5.1. App Review says the app uses both CarPlay Audio and Video entitlements and asks us to remove Video. That explanation does not match the build evidence. The main app's inspected CarPlay entitlements are: com.apple.developer.carplay-driving-task = true com.apple.developer.carplay-video = trueThere is no com.apple.developer.carplay-audio entitlement in the inspected main app or Live Activity extension. We checked the archive and a fresh App Store distribution re-export. More importantly, Apple's own App Store Connect metadata for the actual uploaded Build 27 shows Driving Task and Video, with no Audio entitlement. We explained this discrepancy on November 4 and asked Apple to identify where Audio was detected. On November 5, we received the same rejection explanation again, without an answer to that question. Please identify the specific binary path, bundle identifier, and exact entitlement key/value where Audio was detected. If that finding is incorrect, please correct the rejection reason and explain the actual issue in this build. Repeating the same rejection while ignoring concrete, verifiable evidence is unacceptable. We cannot fix an Audio entitlement that the build evidence does not contain. Please inspect the actual submitted build and provide a specific, actionable explanation.

@Apple when are you reviewing my app?? Its been more than a month since I submitted 1st build.

Hey everyone, I submitted my iOS app (v1.0.4) on Nov 3 and it’s still showing “Waiting for Review” after 3 days. It hasn’t moved to “In Review” yet. Apple sent me a message in the submission thread earlier that day, so I replied with an attachment and resubmitted. Since then there’s been no new message from Apple and nothing else I need to act on in App Store Connect. Is anyone else seeing waits like this recently? And how long did you wait before contacting Apple or requesting an expedited review? Thanks! 🙏

Hello, My app has been stuck in the "Waiting for Review" status for seven days since submission. During my previous submission, it took a total of 37 days to receive a review result—even though the issues raised back then were quick to fix. I have already requested an "Expedited Review" and reached out to the review team via App Store Connect, but I have yet to receive any response or updates. As a solo developer, the ongoing costs I incur while unable to launch my app make this delay a significant burden. Is anyone else experiencing similar review delays recently? If an Apple representative happens to see this post, could you please check the status of my app’s review? I can provide the App ID or further details regarding the submission if needed. Thank you.

Hello, Our app has been in "In Review" status since October 25, 2026 — 12 days now, with no messages or requests from App Review. App: Ryla: Photo Looks & Filters (Apple ID 6821447421) Submission ID: bbe1d65e-6429-4c33-9a25-7c2128f6c8a8 Items: version 1.0 (build 10), two auto-renewable subscriptions, a subscription group and three consumable in-app purchases Developer Support case: 103001645719 Timeline: Oct 12: first submission Oct 25: rejected under Guideline 1.1 (screenshots); we replaced the flagged screenshots and previews and resubmitted the same day Oct 25 → today: "In Review", no further updates We have also requested an expedited review and replied to our Developer Support case. Agreements, tax and banking are all active, and there are no unanswered messages in App Store Connect. Could someone from App Review please check whether this submission is stuck? We're happy to provide a demo video, test details or anything else needed right away. Thank you.

I've been trying to get an app reviewed for over 2.5 months. In these 2.5 months, Apple "reviewed" the app for less than 10 minutes. Apple "rejected" the app 5 times, within 60 seconds after launching the app. Typical rejections include "cant find in-app purchase" or simple questions: "need to understand business model". Rejections come after 10 to 14 days of "Waiting for Review". A reviewer spends 60 seconds in the app before rejecting, and never provides the actual app review. A service that we pay for in our developer program fee. I have opened many support cases during this time. Every single support case goes completely unacknowledged. Apple Support just ghosts me every single time. No email reply. No phone call. No follow up. NO CASE CLOSURE message. No status changes. Nothing. Never once has apple replied to my numerous support cases. COMPLETELY GHOSTED. EVERY. TIME.Such complete and utter lack of responsibility from a support team. There isn't even a way to see what I wrote in the support cases! I might as well talk to myself in the corner. It's equally as effective as raising a support case with Apple Developer Support. Apple - you should know that proper Case Tracking systems exist. You should know that customers want to see the status of a support case. You should know we want to see the words written in our cases? You should know we want to see you replies. You should know, customers expect to see something is being done about support cases? Apple Support provides none of that. I get a list of my old case numbers, and nothing more. Cannot see their status. Cannot see the subject line, nor the messages. Most importantly - there is NEVER a response from Apple. NEVER A SINGLE EMAIL REPLY. NOT ONE. NEVER A STATUS CHANGE. NEVER A CASE CLOSURE. NOTHING. EVER.

I'm genuinely at a loss with Apple's App Review process. Our backend records show that across BOTH reviews, Apple's reviewers did not complete a SINGLE use of our app's core functionality. Not once. ZERO completed generations. For the latest review, our logs confirm Apple successfully logged in, but recorded ZERO generation requests and ZERO credits consumed. This isn't some minor feature. It's the entire foundation of our app. Our app fundamentally changes and becomes personalised as it's used. Without completing that process, you're essentially judging an incomplete product. Submission ID: 6a126514-9bb6-4d91-923c-bf29aacb1b68 Here's why this is so frustrating. We spent months deliberately building an app that offers functionality and a user experience fundamentally different from existing competitors. This wasn't another copycat app - avoiding that was central to its design from day one. We explained these differences extensively in our App Review notes. Yet Apple has rejected us TWICE under Guideline 4.3(b) — Design Spam. We even provided a narrated walkthrough demonstrating exactly what makes our app unique. Our video analytics show ZERO views. So we're being rejected for supposedly lacking originality, despite neither review producing a completed use of our main feature and no recorded views of our demonstration. After both rejections, we've received nothing but generic responses telling us to improve the app, without identifying a single specific problem. How are independent developers supposed to fix something when Apple won't explain what's wrong? We've now filed a formal appeal, which could take a month, with no visible queue position, progress updates or estimated timeframe. Meanwhile, we've already missed multiple planned marketing opportunities, and waiting could mean missing even more. We're not asking for guaranteed approval. We're asking for a fair review of what we've actually built. Has anyone else experienced this? What would you do? Wait for the appeal, hoping the App Review Board properly evaluates the app, even if it takes another month and we miss more deadlines? Withdraw the appeal and resubmit, hoping for a different reviewer, but risking another rejection without proper testing and further warnings against our developer account? I'd genuinely appreciate advice from anyone who's experienced something similar, especially those who've successfully appealed a 4.3(b) rejection. At this point, I genuinely don't know whether this is a reviewer misunderstanding, an automated rejection process, or something else entirely. But how can Apple determine that an app lacks originality when its defining functionality hasn't even been tested?

Hi everyone, I submitted my first app to the App Store on November 5, and App Store Connect still shows “Waiting for Review.” For those who’ve submitted their first app recently, how long did you wait before the status changed to “In Review”? I’d also appreciate any advice on when it makes sense to follow up with App Review. Thanks for sharing your experience!

Hello Apple Developer Community and App Store Commerce team, I am looking for guidance on the review workflow for the first In-App Purchases of my app, Capture Link: UVC Monitor (Apple App ID: 6818688239). The first IAPs were submitted on October 5, 2026: Monthly auto-renewable subscription (Apple IAP ID: 6818721468) Non-consumable lifetime unlock (Apple IAP ID: 6818721648) Subscription group (ID: 22435932) Our macOS app (1.0, Build 16) is approved and Ready for Distribution. The current iPadOS app (1.0, Build 17) and both IAPs still show Waiting for Review on November 6. We verified in App Store Connect that the iPadOS review submission submitted November 3 contains the app version, monthly subscription, lifetime unlock, and subscription group. The current statuses show no rejection or developer action required for these items. The Paid Apps Agreement is active, banking is available, tax documents are in use, and IAP metadata and review screenshots have been supplied. We received confirmation of an expedited app review request on November 2. A production user has reported that purchase options cannot be loaded. I understand from an App Store Commerce Engineer reply that unapproved IAPs are not returned to production StoreKit. My questions: Given that the four items are included in the iPadOS review submission, is there any other first-IAP submission requirement we may have missed? Is this combination of states expected while iPadOS Build 17 is still Waiting for Review, or could it indicate a review workflow issue? What diagnostics or details would help Developer Support distinguish a normal queue delay from a stuck first-IAP workflow without withdrawing the existing submission? I have opened formal support inquiries and am seeking technical guidance here rather than requesting a separate expedited review. Thank you for any insight.

Hi all, I'm trying to stay patient, but I've run out of options and would really appreciate any help, from Apple or from anyone who has been through this. My app's first version with auto-renewable subscriptions has been in review since September. Timeline: Rejected on 4 October (Guideline 3.1.1). Fair enough, fixed and resubmitted on 15 October. Waited 13 days. Rejected on 28 October under Guideline 2.3.2, because my monthly and yearly subscriptions have identical promotional images. App Review asked me to make them unique or delete them. I replied on the submission within 20 minutes. No response, and none to the two follow-up messages I've left there since. The problem is that I can't do what App Review asked. In App Store Connect the image on both subscriptions is locked: no remove (—) option on hover, and the + / upload control doesn't open, in Chrome and Safari, with drag-and-drop too. Apple's docs say removed items can't be added back to the same submission, so I haven't removed the subscriptions. I've deactivated the only offer code, there are no win-back offers, and App Store Promotion was never enabled. New, distinct images are ready to upload. On the support side, I opened case 103005026336 on 28 October. I spoke to someone who was genuinely lovely and said they'd follow up, but that was a week ago and I haven't heard anything since. I've also requested an expedited review and booked an App Review appointment, the earliest available on 10 November. I resubmitted on 30 October with an explanation in the review notes, and it has been "Waiting for Review" ever since. My real question: should I cancel and start a completely fresh submission with new subscription products, and go to the back of the queue again? Or keep waiting? Weeks are turning into months, and the Android version has been approved and waiting the whole time. If anyone from Apple sees this, case 103005026336 is still unresolved, and all I need is the image field unlocked or someone to tell me how to proceed. Thank you.

From my understanding, there are many developers experiencing exceeding long app review times, without any feedback or decision being made. As of currently, there is no known major event or announcement that was made in regards to the delay, or when we can expect to possibly hear anything back.. With that being said, I am in need of help for my AppStore Connect Review. If a decision or feedback is temporarily not an option due to the department being temporarily overwhelmed, it would be nice if someone could provide me with a new app processing timeline to accurately reflect the delay... Just so I know when I should become concerned or consider the possibility of my app being stuck in some recipient error. I requested an "expedite" that is more so to highlight the apps current status rather than actually being expedited, FYI but here is that current ticket number to help better identify me and the app in question. CASE ID 30000004085903

Our app Powerful Progress: Goal Coach (Apple ID 6809707414) was resubmitted on October 31, 2026 after fixing the issues from the previous review (Guidelines 2.1(b), 3.1.1 and 4). It has been "In Review" since then with no messages from App Review. The submission includes version 1.0 (26), a first subscription group with two auto-renewable subscriptions, and a Lifetime In-App Purchase. We also sent an expedite request on November 4. Is there anything we can do or provide to help complete the review? Submission ID: a1b9ab04-923f-45ac-ba61-76dae5046341

Our app Ring-Ring® (Apple ID 6799744191), version 1.0 (build 1968), with its first in-app subscriptions, has been Waiting for Review since 31 October 2026. An expedited review was granted on 3 November, and we contacted App Review (case 30000003800448). The status has not changed since. The app is live on Google Play with paying members. Could someone from App Review take a look? Thank you.

Hello everyone, My app has been stuck in the "In Review" status in App Store Connect for over a month, with no updates or communication from the App Review team. I understand that the review process can sometimes take longer than expected, but waiting more than 30 days without any feedback seems unusual. Has anyone experienced a similar situation recently? Could someone from Apple Developer Support or the App Review team please look into this and help clarify why the review is taking so long? App details: Status: In Review Waiting for Review: Oct 7, 2026 Waiting time: Over 30 days Developer Rejected: Oct 21 In Review: Oct 23 Platform: iOS / App Store Connect I would really appreciate any help or guidance. I just want to get my app reviewed and understand if there is anything blocking the process. Thank you!

I've built a new app and have submitted for review. It went into review almost 6 days ago. But no feedback, no rejection, no approval? Did the sole person reviewing my app suddenly die or something? Or maybe quit without finishing? What can I do? I've never had an app take more than a few hours once it goes into review. This is incredibly frustrating.

Hello everyone, I'm hoping to get some assistance or hear from other developers who have experienced prolonged delays with Apple's App Review process, particularly rejections under Guideline 4.3(a) (Design - Spam). App ID: 6812309771 Our timeline: September 21, 2026: Our app received a rejection under Guideline 4.3(a). September 28, 2026: We submitted a detailed response through the Resolution Center addressing Apple's concerns. October 6, 2026: After receiving no response, we followed up again through the Resolution Center. October 10, 2026: We still have not received any response or update. We have also submitted a formal appeal to the App Review Board. It has now been 19 days since the original rejection and 12 days since our initial response, with no communication from App Review. Our application is not simply a generic template or a repackaged website. It includes substantial interactive functionality built specifically for this application's community, including: Events system: Users can discover events, view event details, and interact with events directly within the application. Community feed: Members can create posts, share content, and interact with posts from other members. User profiles: Members can create and manage their profiles and actively participate in the community. Community rooms: Dedicated spaces for members to communicate and engage around specific topics or groups. Forms and interactive features: Functionality that allows members to submit information and interact directly with the community. These are functional, interactive components of the application rather than static content or a simple repackaging of another app. We have already provided explanations addressing the rejection and are happy to provide any additional information or clarification needed. Our primary concern at this point is the complete lack of communication. We understand that reviews can take additional time, but we have no visibility into whether our responses are being reviewed or whether the case is still actively being handled. We would greatly appreciate assistance from Apple in confirming: Whether our app's review is still active and our Resolution Center responses have been received. Whether anything further is required from us to move the review forward. Whether our formal appeal has been successfully received and is awaiting review. Has anyone else experienced similar delays with Guideline 4.3(a) rejections recently? If someone from Apple's App Review team sees this post, we would sincerely appreciate assistance in looking into our case. Thank you for your time and consideration.